OCPBUGS-89356: build(operator): drop hypershift-no-cgo from operator container images by yiraeChristineKim · Pull Request #8760 · openshift/hypershift

yiraeChristineKim · 2026-06-17T16:09:04Z

This is a cherry-pick of PR #8601 onto release-4.18.

What this PR does / why we need it

Remove the hypershift-no-cgo and hcp binaries from Containerfile.operator. The non-FIPS binary causes Enterprise Contract FIPS violations in Konflux builds for MCE.

Fixes: OCPBUGS-89356
Upstream: #8601

Made with Cursor

Remove the hypershift-no-cgo statically compiled binary and the hcp product CLI from Containerfile.operator, as these are only required in the Konflux build pipeline and not in the operator image itself. Non-Konflux Dockerfiles (Dockerfile, Dockerfile.dev) are unchanged and continue to include hypershift-no-cgo and hcp. Signed-off-by: yiraeChristineKim <yikim@redhat.com> Commit-Message-Assisted-by: Claude (via Claude Code) Co-authored-by: Cursor <cursoragent@cursor.com>

openshift-merge-bot · 2026-06-17T16:09:06Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

openshift-ci-robot · 2026-06-17T16:09:10Z

@yiraeChristineKim: This pull request references Jira Issue OCPBUGS-89356, which is invalid:

expected the bug to target the "4.18.z" version, but no target version was set
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected dependent Jira Issue OCPBUGS-89338 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead
expected dependent Jira Issue OCPBUGS-89338 to target a version in 4.19.0, 4.19.z, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

coderabbitai · 2026-06-17T16:09:13Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 46e1e237-d2a7-4b6a-b01e-e0318ec9f378

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

openshift-ci · 2026-06-17T16:09:21Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

yiraeChristineKim · 2026-06-17T17:22:45Z

/retest

yiraeChristineKim · 2026-06-17T17:23:47Z

/test ci/prow/unit

yiraeChristineKim · 2026-06-17T17:24:40Z

/ok-to-test

yiraeChristineKim · 2026-06-17T17:30:43Z

/jira refresh

openshift-ci-robot · 2026-06-17T17:30:47Z

@yiraeChristineKim: This pull request references Jira Issue OCPBUGS-89356, which is invalid:

expected the bug to target the "4.18.z" version, but no target version was set
expected dependent Jira Issue OCPBUGS-89355 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead
expected dependent Jira Issue OCPBUGS-89355 to target a version in 4.19.0, 4.19.z, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

yiraeChristineKim · 2026-06-17T17:35:37Z

/jira refresh

openshift-ci-robot · 2026-06-17T17:35:44Z

@yiraeChristineKim: This pull request references Jira Issue OCPBUGS-89356, which is invalid:

expected the bug to target the "4.18.z" version, but no target version was set
expected Jira Issue OCPBUGS-89356 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

yiraeChristineKim · 2026-06-17T17:45:20Z

/jira refresh

openshift-ci-robot · 2026-06-17T17:45:26Z

@yiraeChristineKim: This pull request references Jira Issue OCPBUGS-89356, which is invalid:

expected the bug to target the "4.18.z" version, but no target version was set
expected Jira Issue OCPBUGS-89356 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

yiraeChristineKim · 2026-06-17T17:45:59Z

/jira refresh

openshift-ci-robot · 2026-06-17T17:46:06Z

@yiraeChristineKim: This pull request references Jira Issue OCPBUGS-89356, which is invalid:

expected Jira Issue OCPBUGS-89356 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

yiraeChristineKim · 2026-06-17T17:52:40Z

/jira refresh

openshift-ci-robot · 2026-06-17T17:52:45Z

@yiraeChristineKim: This pull request references Jira Issue OCPBUGS-89356, which is invalid:

expected dependent Jira Issue OCPBUGS-89355 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

yiraeChristineKim · 2026-06-18T00:24:20Z

/test e2e-aws

yiraeChristineKim · 2026-06-18T14:23:04Z

/test e2e-aws

openshift-merge-bot · 2026-06-25T19:18:30Z

Scheduling required tests:
/test e2e-conformance

csrwng · 2026-06-25T19:18:41Z

/verified later @yiraeChristineKim

openshift-ci-robot · 2026-06-25T19:18:54Z

@csrwng: This PR has been marked to be verified later by @yiraeChristineKim.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci · 2026-06-25T19:20:32Z

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: yiraeChristineKim

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci · 2026-06-25T21:03:36Z

@yiraeChristineKim: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

celebdor · 2026-06-26T11:02:06Z

/jira refresh

openshift-ci-robot · 2026-06-26T11:02:11Z

@celebdor: This pull request references Jira Issue OCPBUGS-89356, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

celebdor · 2026-06-26T11:02:43Z

/jira refresh

openshift-ci-robot · 2026-06-26T11:02:49Z

@celebdor: This pull request references Jira Issue OCPBUGS-89356, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-89355 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-89355 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
bug has dependents

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-06-26T11:03:46Z

@yiraeChristineKim: Jira Issue OCPBUGS-89356: All pull requests linked via external trackers have merged:

openshift/hypershift#8760

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-89356 has been moved to the MODIFIED state.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 17, 2026

openshift-ci Bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/needs-area labels Jun 17, 2026

yiraeChristineKim marked this pull request as ready for review June 17, 2026 16:14

openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 17, 2026

openshift-ci Bot requested review from isco-rodriguez and sjenning June 17, 2026 16:16

openshift-ci Bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Jun 17, 2026

celebdor added the area/ci-tooling Indicates the PR includes changes for CI or tooling label Jun 22, 2026

openshift-ci Bot removed the do-not-merge/needs-area label Jun 22, 2026

csrwng added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Jun 25, 2026

openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Jun 25, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 26, 2026

celebdor merged commit f0bf6ce into openshift:release-4.18 Jun 26, 2026
13 of 14 checks passed

Uh oh!

Conversation

yiraeChristineKim commented Jun 17, 2026

What this PR does / why we need it

Uh oh!

openshift-merge-bot Bot commented Jun 17, 2026

Uh oh!

openshift-ci-robot commented Jun 17, 2026

What this PR does / why we need it

Uh oh!

coderabbitai Bot commented Jun 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

openshift-ci Bot commented Jun 17, 2026

Uh oh!

yiraeChristineKim commented Jun 17, 2026

Uh oh!

yiraeChristineKim commented Jun 17, 2026

Uh oh!

yiraeChristineKim commented Jun 17, 2026

Uh oh!

yiraeChristineKim commented Jun 17, 2026

Uh oh!

openshift-ci-robot commented Jun 17, 2026

Uh oh!

yiraeChristineKim commented Jun 17, 2026

Uh oh!

openshift-ci-robot commented Jun 17, 2026

Uh oh!

yiraeChristineKim commented Jun 17, 2026

Uh oh!

openshift-ci-robot commented Jun 17, 2026

Uh oh!

yiraeChristineKim commented Jun 17, 2026

Uh oh!

openshift-ci-robot commented Jun 17, 2026

Uh oh!

yiraeChristineKim commented Jun 17, 2026

Uh oh!

openshift-ci-robot commented Jun 17, 2026

Uh oh!

yiraeChristineKim commented Jun 18, 2026

Uh oh!

yiraeChristineKim commented Jun 18, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 25, 2026

Uh oh!

csrwng commented Jun 25, 2026

Uh oh!

openshift-ci-robot commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

celebdor commented Jun 26, 2026

Uh oh!

openshift-ci-robot commented Jun 26, 2026

Uh oh!

celebdor commented Jun 26, 2026

Uh oh!

openshift-ci-robot commented Jun 26, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Jun 26, 2026

What this PR does / why we need it

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

coderabbitai Bot commented Jun 17, 2026 •

edited

Loading